Communication management for core network

ABSTRACT

Systems and methods for managing communications among a central entity and multiple local entities in a telecommunication core network are disclosed. Localized central entities may be established across the core network based on localization patterns of telecommunication devices. The localized central entities may duplicate a portion of central entity data and provide local entities more efficient access to the data.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/296,992, entitled COMMUNICATION MANAGEMENT FOR CORE NETWORK and filedon Oct. 18, 2016, the disclosure of which is incorporated herein byreference.

BACKGROUND

A core network (also known as network core or backbone network) is thecentral part of a telecommunications network that provides variousservices to telecommunication devices, often referred to as userequipment (“UE”), that are connected by access network(s) of thetelecommunications network. Typically, a core network includes highcapacity communication facilities that connect primary nodes, andprovides paths for the exchange of information between differentsub-networks.

Nodes in a core network may include network components (e.g., switchesand routers) that are capable of receiving, sending, or forwardingelectronic information over communication links. Physically, one or moreof core network functionalities (e.g., authentication, callcontrol/switching, service invocation, accounting, or the like) maysimultaneously be implemented in a given core network node. Certain corenetwork nodes may be associated with central entities, such as a centraldatabase that contains details of each telecommunication devicesubscriber that is authorized to use the core network (e.g., the homelocation register (HLR) in GSM networks, home subscriber server (HSS) oruser profile server function (UPSF) in IMS networks, or the like). Thecentral entity may communicate with nodes associated with multiple localentities (e.g., visitor location registers (VLRs), serving GPRS supportnodes (SGSNs), mobility management entities (MMEs), or the like)distributed across the core network to manage and provide services tovarious telecommunication devices.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages will becomemore readily appreciated as the same become better understood byreference to the following detailed description, when taken inconjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram depicting an illustrative telecommunicationenvironment;

FIG. 2 is an illustrative diagram depicting a core network includinglocalized central entities;

FIG. 3 is a flow diagram depicting an illustrative routine forselectively transferring data from a central entity to localized centralentities; and

FIG. 4 is a flow diagram depicting an illustrative routine forrequesting data from localized central entities.

DETAILED DESCRIPTION

Generally described the present disclosure relates to the management ofcommunications among central entities and local entities in a corenetwork of a telecommunications network. More specifically, aspects ofthe present application correspond to the establishment of localizedcentral entities that maintain a portion of central entity data andprovide efficient communications with local entities in accordance withmobility patterns of telecommunication devices associated with thetelecommunications network.

A core network, network core, or backbone network, is the central partof a telecommunications network that provides various services totelecommunication devices connected by access networks. One of the mainfunctions of the core network is to route telephone calls, messages, orother data across a public switched telephone network (PSTN) or IPMultimedia Subsystem (IMS). The core network may provide high capacitycommunication facilities that connect various nodes, allowing the nodesto exchange information via various paths.

Certain core network nodes may be associated with central entities, suchas a single central database that contains details of eachtelecommunication device subscriber that is authorized to use the corenetwork (e.g., the home location register (HLR) in GSM networks, homesubscriber server (HSS) or user profile server function (UPSF) in IMSnetworks, or the like). The central entity may communicate with nodesassociated with various local entities (e.g., visitor location register(VLR), serving GPRS support node (SGSN), mobility management entity(MME), or the like) within the core network to manage and provideservices (e.g., authentication, service invocation, or the like) tovarious telecommunication devices. Each distinct type of local entitiesmay be distributed in multiple entities across the entire core networkor some portion thereof, depending on corresponding functionality,traffic pattern, or network topology.

Illustratively, a central entity, such as an HLR, may be physicallylocated in a centralized location mostly driven by geographical optimumselection based on network traffic concentration and pattern. The HLRmaintains the record of all the provisioned subscriber data, subscriberssubscription details, supplementary service data, present locationinformation, or data related to telecommunication devices subscribed toor otherwise associated with the telecommunications network (generallyreferred to as “mobile subscribers”). The HLR also maintains the presentaddresses of various local entities that serve mobile subscribes.Accordingly, the HLR interacts with the local entities, such as mobileswitching center (MSC), visiting location register (VLR), serving GPRSsupport node (SGSN), mobility management entity (MME), or the like, thatare more locally diverse and distributed across the core network.

Because of the mobility nature of mobile subscribers, an enormous amountof traffic may constantly occur between the central entity (e.g., HLR)and multiple local entities (e.g., MSCs, VLRs, SGSNs, MMES) of varioustypes. This allows the central entity to remain informed and updatedabout the present location information of mobile subscribers in thetelecommunications network so that such information can be used toproperly initiate or terminate voice calls, data sessions, deliveringshort message service (SMS), multimedia messaging service (MMS) andother telecommunications network services.

Geographically, not many mobile subscribers frequently travel amonglocations (e.g., another state or city) that are relatively far from oneanother. A majority of mobile subscribers may be on the move from timeto time, however they largely remain within a relatively small andstable geographic area (e.g., a same city or county). The mobilitypatterns of mobile subscribers may be utilized to establish localizedcentral entities in the core network that maintain portions of centralentity data for “local” mobile subscribers. The localized centralentities may be located on nodes closer (in terms of geographic distanceor network topology) to corresponding local entities thus providing themfaster and more efficient access. Therefore, local entities may nolonger need to interact with the central entity for a substantial amountof data related to “local” mobile subscribers associated with the localentities. Accordingly, number of transactions and other overheadassociated with the communications between central and local entitiescan be greatly reduced.

Although aspects of the present disclosure will be described with regardto an illustrative telecommunications environment and componentinteractions, communication protocols, flow diagrams and userinterfaces, one skilled in the relevant art will appreciate that thedisclosed embodiments are illustrative in nature and should not beconstrued as limiting. Specifically, although the term telecommunicationdevice is used in this document, the term represents any type of devicehaving a component for communicating with one or more other devices viaone or more communication paths. Such communication paths can includewireless communication paths (via infra-red, RF, optical, terrestrial,or satellite communication media) and wired communication paths.Additionally, although the present disclosure references atelecommunication device, one skilled in the relevant art willappreciate that a telecommunication device may also be referred to as awireless computing device, a mobile communication device, a mobiledevice, or a computing device. Accordingly, reference to atelecommunication device should not be interpreted as including anyparticular functionality or operation not described in the presentdisclosure. Still further, although the present disclosure is describedwith regard to specific methodologies and frameworks for datarequesting, retrieval, collection, or updating, the present disclosureshould not be construed to require combination of the disclosedembodiments or any specific variation unless such combination orvariation is expressly identified.

With reference now to FIG. 1, a block diagram depicting an illustrativetelecommunication environment 100 will be described. Thetelecommunication environment 100 can include a number oftelecommunication devices 122, each associated with a user. Thetelecommunication devices 122 can correspond to a wide variety ofdevices or components that are capable of initiating, receiving orfacilitating communications over a communication network including, butnot limited to, personal computing devices, electronic book readers(e.g., e-book readers), hand held computing devices, integratedcomponents for inclusion in computing devices, home electronics,appliances, vehicles, machinery, landline telephones, network-basedtelephones (e.g., voice over IP (“VoIP”), cordless telephones, cellulartelephones, smart phones, modems, personal digital assistants, laptopcomputers, gaming devices, media devices, and the like. In anillustrative embodiment, the telecommunication devices 122 include awide variety of software and hardware components for establishingcommunications over one or more communication networks, including anaccess network 120, a core network 110, or other private or publicnetworks such as network 130.

The telecommunication devices 122 are communicatively connected via theaccess network 120, such as GSM EDGE Radio Access Network (GRAN), GSMEDGE Radio Access Network (GERAN), Universal Terrestrial Radio AccessNetwork (UTRAN), Evolved Universal Terrestrial Radio Access (E-UTRAN),or the like. Illustratively, the access network 120 is distributed overland areas called cells, each served by at least one fixed-locationtransceiver, known as a cell site or base station. The base stationprovides the cell with the network coverage which can be used fortransmission of voice, messages, or other data. A cell might use adifferent set of frequencies from neighboring cells, to avoidinterference and provide guaranteed service quality within each cell.When joined together these cells provide radio coverage over a widegeographic area. This enables a large number of telecommunicationdevices 122 to communicate via the fixed-location transceivers. Althoughthe access network 120 is illustrated as a single network, one skilledin the relevant art will appreciate that the access network can beinclude any number of public or private communication networks and/ornetwork connections.

The telecommunication environment 100 includes the core network 100 thatprovides various services to telecommunication devices 122 that areconnected via the access network 120. One of the main functions of thecore network is to route telephone calls, messages, or other data acrossa public switched telephone network (PSTN) or IP Multimedia Subsystem(IMS). The core network may provide high capacity communicationfacilities that connect various nodes implemented on one or morecomputing devices, allowing the nodes to exchange information viavarious paths.

Certain core network nodes may be associated with central entities 112,such as a single central database that contains details of eachtelecommunication device subscriber that is authorized to use the corenetwork (e.g., the home location register (HLR) in GSM networks, homesubscriber server (HSS) or user profile server function (UPSF) in IMSnetworks, or the like). The central entity 112 may communicate withnodes associated with various local entities 114 (e.g., visitor locationregisters (VLRs), serving GPRS support nodes (SGSNs), mobilitymanagement entities (MMEs), or the like) within the core network tomanage and provide services (e.g., authentication, service invocation,or the like) to various telecommunication devices 122.

Illustratively, a central entity 112, such as an HLR, may be physicallylocated in a centralized location mostly driven by geographical optimumselection based on network traffic concentration and pattern. The HLRmaintains the record of all the provisioned subscriber data, subscriberssubscription details, supplementary service data, present locationinformation, or other data related to mobile subscribers. The HLR alsomaintains the present addresses of various local entities 114 that servemobile subscribers. Accordingly, the HLR interacts with the localentities, such as mobile switching center (MSC), visiting locationregister (VLR), serving GPRS support node (SGSN), mobility managemententity (MME), or the like, that are more locally diverse and distributedacross the core network 110 (e.g., in different cities, neighborhoods,or other distributed localities).

The core network 100 may be further connected to one or more networks130, which may include any system for allowing multiple computing ortelecommunication devices to communicate with each other. For example,the network 130 can be a Local Area Network (LAN), a Wide Area Network(WAN), a point-to-point network, a wireless network, a satellitenetwork, a cable network, the Internet, combinations of the same, or thelike.

FIG. 2 is an illustrative diagram depicting a core network 110 includinglocalized central entities 212. As discussed earlier, because of themobility nature of mobile subscribers, an enormous amount of traffic mayconstantly occur between a central entity 112 and various local entities114. This allows the central entity 112 to remain informed and updatedabout the present location information of mobile subscribers in thetelecommunication environment 100 so that such information can be usedto properly initiate or terminate voice calls, data sessions, deliveringshort message service (SMS), multimedia messaging service (MMS) andother telecommunications network services.

Geographically, not many mobile subscribers frequently travel amonglocations (e.g., another state or city) that are relatively far from oneanother. A majority of mobile subscribers may be on the move from timeto time, however they largely remain within a relatively small andstable geographic area (e.g., a same city or county). The mobilitypatterns of mobile subscribers may be utilized to establish localizedcentral entities 212 in the core network 110 that maintain portions ofcentral entity data for “local” mobile subscribers. The localizedcentral entities 212 may be located on core network nodes that arecloser (in terms of geographic distance or network topology) to localentities 114 that they serve, thus providing faster and more efficientaccess. Therefore, local entities 114 may no longer need to interactwith the central entity 112 for a substantial amount of data related to“local” mobile subscribers associated with the local entities 114, andtransactions and overhead associated with the communications betweencentral and local entities can be greatly reduced.

In some embodiments, a localized central entity 212 a may be implementedon the same node(s) as a local entity 114 a that it serves. In thiscase, the communications between local entity 114 a and localizedcentral entity 212 a may not involve network-related latencies and thecommunication cost may be negligible. In some embodiments, a localizedcentral entity 212 b may be implemented on certain core network node(s)to exclusively serve a corresponding local entity 114 b. In this case,the physical or network-based distance between the localized centralentity 212 b and the local entity 114 b may be much smaller than thedistance between the central entity 112 and the local entity 114 b.Thus, the network-related latencies or other communication cost forinteractions between the localized central entity 212 b and the localentity 114 b is much smaller. In other embodiments, a localized centralentity 212 c may be implemented on certain core network node(s) to servea group of local entities 114 c, 114 d, or the like. In this case, thegroup of local entities 114 may share a same localized central entity212 c due to proximity among the local entities (e.g., within athreshold distance of one another either geographically or based on corenetwork topology). Similarly, the localized central entity 212 c may belocated much closer to all of the local entities 114 in the group interms of physical distance or network proximity, than the central entity112 does. Thus, the network-related latencies or other communicationcost for interactions between the localized central entity 212 c and anylocal entity 114 in the group is much smaller.

FIG. 3 is a flow diagram depicting an illustrative routine 300 forselectively transferring data from a central entity 112 to localizedcentral entities 212. Routine 300 may be implemented by the centralentity 112 (or an associated computing device or service). At block 310,the central entity 112 analyzes telecommunication device related data todetermine localization pattern of mobile subscribers. In someembodiments, the central entity 112 may analyze telecommunication devicerelated data currently maintained by the central entity 112 anddetermine current geographic locations associated with mobilesubscribers. In some embodiments, the central entity 112 analyzeshistorical telecommunication device related data to determine travelpatterns associated with each mobile subscriber. For example, thecentral entity 112 may compute an estimated geographic location orgeographic region for a mobile subscriber based on the respectivedurations within a specified period of time when the mobile subscriberwas connecting from different locations. Various time-decay factors orother weights may be utilized in the computation. In some embodiments,the central entity 112 may further calculate a measure of geographicstability for each mobile subscriber based on the frequency and distanceof movements of the corresponding telecommunication device 122 for aspecified period of time (which may or may not be the same period oftime used for location determination). Illustratively, higher movementfrequency or longer movement distance may result in a lower measure ofgeographic stability.

At block 320, the central entity 122 associates telecommunicationdevices 122 with local entities 114 based on mobile subscriberlocalization pattern. In some embodiments, the central entity 122 maycalculate physical or network-based distance between a local entity 114and each telecommunication device 122 based on their actual or estimatedlocations. If the distance falls below a threshold, the local entity 114may be considered associated with the telecommunication device 122. Insome embodiments, the central entity 112 may filter outtelecommunication devices 122 that have a relatively low measure ofgeographic stability (e.g., below a specified threshold value), eitherbefore or after the distance calculation. In other embodiments, thecentral entity 112 simply associates a telecommunication device 122 withany local entity 114 that requested, updated, or otherwise accessedcentral entity data related to the telecommunication device 122 mostrecently; the central entity 112 may alternatively associate thetelecommunication device 122 with any local entity 114 that has had suchaccess more than a threshold number of times during a specified periodof time.

At block 330, the central entity 112 creates or identifies localizedcentral entities 212 that serve local entities 114. The central entity112 may analyze the density or quantity of telecommunication device 122associated with each local entity 114, the computational or networkingresources available at local entity nodes or other nearby nodes, or thecost for creating localized central entities 212 at specific locations,and then decide to create localized central entities 212 directly oncertain local entity nodes or on other nodes that may provide relativelyefficient access to one or more local entities. In some embodiments, thecentral entity 112 may decide to terminate previously created localizedcentral entities 212 due to under-utilization or changes in mobilesubscribe localization patterns.

In some embodiments, certain localized central entities 212 may havepreviously been established and the central entity 112 may selectexisting localized central entities 212 to serve local entities 114based on the geographic distance or network proximity between the two.Illustratively, the central entity 112 may send network address or otheridentifiers of a selected localized central entity 212 to a local entity114 and direct the local entity 114 to interact with the selectedlocalized central entity 212. Because localized central entities 212 maybe dynamically created or terminated in accordance with developments inmobile subscriber localization patterns, a local entity 114 may beserved by different localized central entities 212 at different times.

At block 340, the central entity 112 selectively transferstelecommunication device related data from the central entity 112 tovarious localized central entities 212. Illustratively, the centralentity 112 keeps track of the associations between telecommunicationdevices 122 and local entities 114 as well as associations between localentities 114 and localized central entities 212 that serve them. Byconnecting or combining these associations, the central entity 112determines mappings between telecommunication devices 122 and localizedcentral entities 212, selects data entries related to individualtelecommunication devices 122 that are mapped to specific localizedcentral entities 212, and transmits the selected data entries thereto.It should be noted that the data transmitted to different localizedcentral entities 212 may or may not overlap with one another, and notall of the data entries maintained by the central entity 112 may betransmitted to a localized central entity 212

FIG. 4 is a flow diagram depicting an illustrative routine 400 forrequesting data from a localized central entity 212. Routine 400 may beimplemented by a local entity 114. At block 410, the local entity 114generates a data request related to a target telecommunication device122. For example, the data request may correspond to a request for dataabout the SIM, mobile services ISDN number, or other informationmaintained on a central entity 112 that relates to the targettelecommunication device 122.

At block 420, the local entity 114 transmits the data request to alocalized central entity 212. The localized central entity 212 may storecopies of at least a portion of the data maintained by the centralentity 112. As discussed above, in some embodiments, the local entity114 has previously received the network address or other identifier ofthe localized central entity 212 from the central entity 112 or anassociated service, thus the data request can be sent or routed to thelocalized central entity 212 based thereon. In other embodiments, thelocal entity 114 may create or have established a local or dedicatedlocalized central entity 212 independently. Such independentlyestablished localized central entities 212 may be managed or controlledby their corresponding local entity 114, and may or may not be known oraccessible to the central entity 112 or other local entities 114.

At block 430, the local entity 114 determines whether the requested datais successfully retrieved from the localized central entity 212. If therequested data is available at the localized central entity 212 andsuccessfully retrieved, the routine 400 ends. Otherwise, the routine 400proceeds to block 440, where the local entity 114 transmits the datarequest to the central entity 112 and retrieves requested data.

At block 450, either the local entity 114 or the central entity 112further transmits to the localized central entity 212 a copy of therequested data related to the target telecommunication device 122. Insome embodiments, the central entity 112 transmits additional datarelated to the target telecommunication device 122 besides the data asrequested. This ensures that the localized central entity 212 can beupdated with additional or new data related to telecommunication devices122, such as the target telecommunication device, that have recentlytraveled into a geographic or network jurisdiction served by the localentity 114. Subsequently, the localized central entity 212 may respondto future data requests related to the target telecommunication deviceor another device with such updated data.

Depending on the embodiment, certain acts, events, or functions of anyof the methods described herein can be performed in a differentsequence, can be added, merged, or left out altogether (e.g., not alldescribed acts or events are necessary for the practice of thealgorithm). Moreover, in certain embodiments, acts or events can beperformed concurrently, e.g., through multi-threaded processing,interrupt processing, or multiple processors or processor cores or onother parallel architectures, rather than sequentially.

The various illustrative logical blocks, modules and method elementsdescribed in connection with the embodiments disclosed herein can beimplemented as electronic hardware (e.g., application-specific logiccircuitry), computer software executed by hardware, or combinations ofboth. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, and stepshave been described above generally in terms of their functionality.Whether such functionality is implemented as hardware, or as softwareexecuted by hardware, depends upon the particular application and designconstraints imposed on the overall system. The described functionalitycan be implemented in varying ways for each particular application, butsuch implementation decisions should not be interpreted as causing adeparture from the scope of the disclosure.

The various illustrative logical blocks and modules described inconnection with the embodiments disclosed herein can be implemented orperformed by a computing device, such as a general purpose processor, adigital signal processor (DSP), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA) or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general purpose processor can be amicroprocessor, but in the alternative, the processor can be acontroller, microcontroller, or state machine, combinations of the same,or the like. A processor can also be implemented as a combination ofcomputing devices, e.g., a combination of a DSP and a microprocessor, aplurality of microprocessors, one or more microprocessors in conjunctionwith a DSP core, or any other such configuration.

The elements of a method, process, or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module executed by a processor, or in acombination of the two. A software module can reside in RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, harddisk, a removable disk, a CD-ROM or any other form of computer-readablestorage medium known in the art. A storage medium can be coupled to theprocessor such that the processor can read information from, and writeinformation to, the storage medium. In the alternative, the storagemedium can be integral to the processor. The processor and the storagemedium can reside in an ASIC. The ASIC can reside in a user terminal. Inthe alternative, the processor and the storage medium can reside asdiscrete components in a user terminal.

Conditional language used herein, such as, among others, “can,” “might,”“may,” “e.g.,” and the like, unless specifically stated otherwise, orotherwise understood within the context as used, is generally intendedto convey that certain embodiments include, while other embodiments donot include, certain features, elements, and/or states. Thus, suchconditional language is not generally intended to imply that features,elements and/or states are in any way required for one or moreembodiments or that one or more embodiments necessarily include logicfor deciding, with or without author input or prompting, whether thesefeatures, elements and/or states are included or are to be performed inany particular embodiment. The terms “comprising,” “including,”“having,” “involving,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., may beeither X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z).Thus, such disjunctive language is not generally intended to, and shouldnot, imply that certain embodiments require at least one of X, at leastone of Y or at least one of Z to each be present.

Unless otherwise explicitly stated, articles such as “a” or “an” shouldgenerally be interpreted to include one or more described items.Accordingly, phrases such as “a device configured to” are intended toinclude one or more recited devices. Such one or more recited devicescan also be collectively configured to carry out the stated recitations.For example, “a processor configured to carry out recitations A, B, andC” can include a first processor configured to carry out recitation Aworking in conjunction with a second processor configured to carry outrecitations B and C.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it will beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As will berecognized, certain embodiments described herein can be embodied withina form that does not provide all of the features and benefits set forthherein, as some features can be used or practiced separately fromothers. All changes which come within the meaning and range ofequivalency of the claims are to be embraced within their scope.

What is claimed is:
 1. A computer-implemented method for managingcommunications within a core network of a telecommunications networkthat provides services to telecommunication devices, the core networkincluding nodes corresponding to a central entity and a plurality oflocal entities, the method comprising: determining localization patternsof a plurality of telecommunication devices based at least in part onanalysis of data related to the plurality of telecommunication devicesthat utilize the core network; establishing a plurality of localizedcentral entities on the core network based at least in part on thelocalization patterns, wherein each localized central entity isassociated with one or more local entities that the localized centralentity serves; and transferring data related to at least a subset of theplurality of telecommunication devices from the central entity to atleast one localized central entity, wherein the at least one localizedcentral entity receives and responds to requests from the one or moreassociated local entities for data related to one of the subset oftelecommunication devices.
 2. The computer-implemented method of claim1, wherein the core network routes telephone calls, messages, or dataacross a public switched telephone network (PSTN) or IP MultimediaSubsystem (IMS).
 3. The computer-implemented method of claim 1, whereinthe central entity includes a central database on the core network thatmaintains the data related to the plurality of telecommunicationdevices.
 4. The computer-implemented method of claim 1, wherein thecentral entity corresponds to a home location register (HLR) in GSMnetworks, a home subscriber server (HSS) in IMS networks, or a userprofile server function (UPSF) in IMS networks.
 5. Thecomputer-implemented method of claim 1, wherein the data related to theplurality of telecommunication devices include at least one ofprovisioned subscriber data, subscriber subscription details,supplementary service data, or present location information associatedwith individual telecommunication devices.
 6. The computer-implementedmethod of claim 1, wherein the plurality of local entities include atleast one of a mobile switching center (MSC), a visiting locationregister (VLR), a serving GPRS support node (SGSN), or a mobilitymanagement entity (MME).
 7. The computer-implemented method of claim 1,wherein a physical or network-based distance is smaller between the atleast one localized central entity and the associated one or more localentities than between the central entity and the associated one or morelocal entities.
 8. The computer-implemented method of claim 7, whereinthe at least one localized central entity is implemented on a same nodeas one of the associated one or more local entities.
 9. Thecomputer-implemented method of claim 1 further comprising directing, bythe at least one central entity, individual ones of the one or morelocal entities to communicate with individual ones of the plurality oflocalized central entities.
 10. The computer-implemented method of claim1, wherein establishing a plurality of localized central entities on thecore network comprises dynamically creating the plurality of localizedcentral entities.
 11. The computer-implemented method of claim 1,wherein the central entity stores associations between the plurality oftelecommunications devices and the plurality of local entities.
 12. Thecomputer-implemented method of claim 11, wherein the central entitystores associations between the plurality of local entities and theplurality of localized central entities.
 13. The computer-implementedmethod of claim 1 further comprising terminating one or more localizedcentral entities based at least in part on the localization patterns.14. A system for managing communications within a core network of atelecommunications network that provides services to telecommunicationdevices, the core network including nodes corresponding to at least onecentral entity and a plurality of local entities, the core networkcomprising one or more processors on one or more nodes configured to:determine localization patterns of a plurality of telecommunicationdevices based at least in part on analysis of data related to theplurality of telecommunication devices that utilize the core network;establish a plurality of localized central entities on the core networkbased at least in part on the localization patterns, wherein eachlocalized central entity is associated with one or more local entitiesthat the localized central entity serves; and transfer data related toat least a subset of the plurality of telecommunication devices from thecentral entity to at least one localized central entity, wherein the atleast one localized central entity receives and responds to requestsfrom the one or more associated local entities for data related to oneof the subset of telecommunication devices.
 15. The system of claim 14,wherein the data related to the plurality of telecommunication devicesinclude at least one of provisioned subscriber data, subscribersubscription details, supplementary service data, or present locationinformation associated with individual telecommunication devices. 16.The system of claim 14, wherein the plurality of local entities includeat least one of a mobile switching center (MSC), a visiting locationregister (VLR), a serving GPRS support node (SGSN), or a mobilitymanagement entity (MME).
 17. The system of claim 14, wherein a physicalor network-based distance is smaller between the at least one localizedcentral entity and the associated one or more local entities thanbetween the central entity and the associated one or more localentities.
 18. The system of claim 17, wherein the at least one localizedcentral entity is implemented on a same node as one of the associatedone or more local entities.
 19. The system of claim 14, whereinestablishing a plurality of localized central entities on the corenetwork comprises dynamically creating the plurality of localizedcentral entities.
 20. The system of claim 14, wherein the central entitystores associations between the plurality of telecommunications devicesand the plurality of local entities.
 21. The system of claim 20, whereinthe central entity stores associations between the plurality of localentities and the plurality of localized central entities.
 22. The systemof claim 14, wherein the one or more processors is further configured toterminate one or more localized central entities based at least in parton the localization patterns.